Wearable apparatus for continuous blood glucose monitoring

ABSTRACT

A system, a method, and a computer program product for providing wearable continuous blood glucose monitoring. In some embodiments, there is provided a method that includes receiving, at a smartwatch, an alert representative of a glucose state of a host-patient coupled to a glucose sensor; detecting, at the smartwatch, a predetermined action indicative of a request to generate a glance view providing an indication of the glucose state of the host-patient; and presenting, at the smartwatch and in response to the detecting, the glance view providing the indication of the glucose state of the host-patient.

INCORPORATION BY REFERENCE TO RELATED APPLICATIONS

Any and all priority claims identified in the Application Data Sheet, orany correction thereto, are hereby incorporated by reference under 37CFR 1.57. This application claims the benefit of U.S. ProvisionalApplication No. 62/271,843, filed Dec. 28, 2015. Each of theaforementioned applications is incorporated by reference herein in itsentirety, and each is hereby expressly made a part of thisspecification.

FIELD

The present disclosure generally relates to continuous glucosemonitoring.

BACKGROUND

Diabetes mellitus is a disorder in which the pancreas cannot createsufficient insulin. In a diabetic state, a person suffering from highblood sugar may experience an array of physiological side effectsassociated with the deterioration of small blood vessels. These sideeffects may include, for example, kidney failure, skin ulcers, bleedinginto the vitreous of the eye, and the like. A hypoglycemic reaction,such as a low blood sugar event, may be induced by an inadvertentoverdose of insulin, or after a normal dose of insulin orglucose-lowering agent. In a severe hypoglycemic reaction, there may bea high risk for headache, seizure, loss of consciousness, and coma.

A diabetic person may carry a self-monitoring blood glucose (SMBG)monitor which typically requires the user to prick his or her finger tomeasure his or her glucose levels. Given the inconvenience associatedwith traditional finger pricking methods, it is unlikely that a diabeticwill take a timely SMBG measurements and, consequently, may be unawarewhether his or her blood glucose value is indicative of a dangeroussituation.

Consequently, a variety of non-invasive, transdermal (e.g.,transcutaneous) and/or implantable electrochemical sensors are beingdeveloped for detecting and/or quantifying blood glucose values. Thesedevices generally transmit raw or minimally processed data forsubsequent analysis at a remote device. The remote device may have adisplay that presents information to a user hosting the sensor. In somesystems, a patient may check his or her glucose level on a hand heldcomputing device. There are challenges to presenting this informationdiscreetly and reliably.

SUMMARY

Methods and apparatus, including computer program products, are providedfor wearable continuous blood glucose monitoring.

In some embodiments, there is provided a method that includes receiving,at a smartwatch, an alert representative of a glucose state of ahost-patient coupled to a glucose sensor; detecting, at the smartwatch,a predetermined action indicative of a request to generate a glance viewproviding an indication of the glucose state of the host-patient; andpresenting, at the smartwatch and in response to the detecting, theglance view providing the indication of the glucose state of thehost-patient.

In some embodiments, there is provided a method that includesdetermining a quantity of followers being monitored via a dashboard viewpresented at a display of the smartwatch, the dashboard view including aplurality of icons corresponding to a plurality of host-patients, eachof which having a corresponding glucose state; generating a displayincluding the plurality of icons sized according to the determinedquantity of followers; receiving a selection of a sized icon from amongthe plurality of icons; and displaying additional information regardingthe corresponding glucose state of the host-patient corresponding to theselected, sized icon.

In some embodiments, there is provided a method that includes receiving,at a smartwatch, an alert representative of a glucose state of ahost-patient coupled to a glucose sensor; presenting, at the smartwatch,a user interface view representative of the glucose state; receiving arequest to allow a handoff of the presented user interface view toanother device; and presenting, at the other device and in response tothe handoff, the user interface view.

In some implementations, there is provided a method of presenting anotification bar in the glance view in response to an alert; detecting auser input to view the notification bar. The user input can be a fingerswipe or a manipulation of a physical button. The notification bar caninclude at least one actionable selection. The actionable selection candisplay a map, displays a glucose trend chart, acknowledges the alert,or dismisses the alert.

In some implementations, the current subject matter can include one ormore of the features disclosed herein including the following optionalfeatures. The alert may be received via a low power radio accesstransceiver at the smartwatch. The low power radio access transceivermay be configured in accordance with at least one of Bluetooth,Bluetooth Low Energy, or NFC. The alert may be received from a receiverwirelessly coupled to the glucose sensor via transmitter sensorelectronics. The receiver may include at least one of a smartphoneand/or a tablet. The receiver may include a continuous blood glucoseapplication configured to interact with the smartwatch. The alert may bereceived from a remote server. The detecting of the predetermined actionmay trigger the smartwatch to replace a home screen and/or a defaultuser interface view with the glance view. The smartwatch may trigger, inresponse to the detecting, a feedback comprising a haptic indicator, anaudio indicator, and/or a visual indicator. The predetermined action mayinclude a selection of a certain icon displayed on the smartwatch. Thepredetermined action may include a selection of a physical button. Thepredetermined action may include a detection of a certain wristmovement. The predetermined action may include a detection of a certaineye movement of a wearer of the smartwatch. A swipe pattern may bedetected. The detected swipe pattern may be mapped to at least one of aplurality of glance views, each of which is mapped to a different swipepattern; and the at least one glance view may be presented based on thedetected swipe pattern. The glucose state may be mapped to at least oneof a plurality of glance views, each of which is mapped to a differentglucose state; and the at least one glance view may be presented basedon the glucose state. The role of a wearer of the smartwatch may bedetermined. The role may be mapped to at least one of a plurality ofglance views, each of which is mapped to a different role; and the atleast one glance view may be presented based on the determined role. Theglance view may be presented based on what the smartwatch is directlycoupled to. The glance view may provide, in a single user interfaceview, a graphical indication of the glucose state including a rate ofchange of the glucose state. The rate of change may be represented by aquantity of arrows presented via the glance view. The glucose glanceview may include a current glucose value. A dashboard may be generated,wherein the dashboard may include a plurality of icons corresponding toa plurality of host-patients, each of which having a correspondingglucose state. At least one of the plurality of icons may be selected inorder to obtain additional information regarding the correspondingglucose state. The size of the plurality of icons may be varied based ona quantity of the plurality of icons. An order of presentation for theplurality of icons may be varied based on a severity of thecorresponding glucose state. The glance view presented at the smartwatchmay be handed off to another device to enable presentation of the glanceview at the other device.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive. Further features and/or variations may beprovided in addition to those set forth herein. For example, theimplementations described herein may be directed to various combinationsand subcombinations of the disclosed features and/or combinations andsubcombinations of several further features disclosed below in thedetailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and constitutea part of this specification, show certain aspects of the subject matterdisclosed herein and, together with the description, help explain someof the principles associated with the subject matter disclosed herein.In the drawings,

FIG. 1 illustrates a continuous analyte sensor system, in accordancewith some example embodiments;

FIG. 2 illustrates a functional block diagram of a mobile device usedwith the continuous analyte sensor system, in accordance with someexample embodiments;

FIG. 3A illustrates an example of a smartwatch including a glance view,in accordance with some example embodiments;

FIG. 3B illustrates an example of a smartwatch including a glance viewand notification bar, in accordance with some example embodiments;

FIG. 3C illustrates an example of a process for triggering the displayof a glance view on a smartwatch, in accordance with some exampleembodiments;

FIGS. 4A-B illustrate examples of smartwatches including dashboards, inaccordance with some example embodiments;

FIG. 4C depicts an example of a process for generating dashboards, inaccordance with some example embodiments;

FIGS. 5A-B illustrate examples of smartwatches configured to handoff adisplay, in accordance with some example embodiments;

FIG. 5C depicts an example of a process for providing handoffs, inaccordance with some example embodiments

FIG. 6 depicts an example of devices locally coupled, in accordance withsome example embodiments; and

FIG. 7 depicts a block diagram of a smartwatch, in accordance with someexample embodiments.

Like labels are used to refer to same or similar items in the drawings.

DETAILED DESCRIPTION

Wearable devices, such as smartwatches, may provide an additional way toprovide alerts regarding blood glucose level measurements as well asother types of information and reports to a wearer of the smartwatch.The smartwatch user may be a host-patient being monitored by acontinuous blood glucose sensor that wirelessly transmits alerts andother information to a receiver, such as a smartphone, a tablet, acomputer, and/or any other device. The smartwatch may receive alerts andother information wirelessly directly from a transmitter associated withthe sensor (for example, over a low power radio access technology suchas Bluetooth, Bluetooth Low Energy, NFC, etc. or other radio technologyincluding WiFi, cellular, etc.). Alternatively or additionally, thesmartwatch may receive alerts and other information wirelessly from thereceiver (for example, over a low power radio access technology such asBluetooth, Bluetooth Low Energy, NFC, etc. or other radio technologyincluding WiFi, cellular, etc.). Alternatively or additionally, thesmartwatch may receive alerts and other information wirelessly from anyother device, such as a cloud-coupled server.

Although the smartwatch may be beneficial to alerting and monitoringblood glucose and other types of data, the smartwatch may becharacterized as having limited display area, when compared to otherdisplay devices, such as a smartphone.

In some example embodiments, there may be provide a smartwatch thatreceives alerts related to blood glucose monitoring, and the alertsand/or reports associated with the alerts may be presented as a userinterface view that takes into account the limited display size of thesmartwatch.

Before providing additional details for the smartwatch disclosed herein,the following provides an example system description in which thesmartwatch disclosed herein may be implemented.

FIG. 1 is a schematic view of a continuous analyte sensor system 100coupled to a host, such as a patient, and communicating with a number ofdevices 110-113, in accordance with some example embodiments.

In some example embodiments, a host-patient may wear a sensor assembly101 as well as smartwatch 199A. The smartwatch may couple wirelessly toa sensor assembly 101 via for example low energy links, such as NFC,Bluetooth, and/or Bluetooth Low Energy, although other radiotechnologies may be used as well including WiFi and cellular.Alternatively or additionally, smartwatch 199A may couple wirelessly toone or more receivers 110-113 (which may be via low energy links and/orother radio technologies), and the receiver may then couple to theserver 130 via the cellular network, the Internet, and/or other types ofnetworks and/or links including wireless links and/or wired links.Alternatively or additionally, smartwatch 199A may couple (via wiredand/or wireless links) to server 130. In this way, the smartwatch 199Amay receive alerts from the sensor assembly 101, receiver 110-113,and/or server 130.

In some example embodiments, a smartwatch 199B may be worn by someoneother than a host-patient. For example, smartwatch 199B may be worn by aremote follower, such as a caregiver, a parent, a teacher, a nurse,and/or any other entity. The remote follower wearing smart watch 199Bmay receive the same, similar, or different alerts, reports, and/or thelike as the host-patient being followed and is wearing smartwatch 199A.Moreover, the remote follower's smartwatch 199B may receive the alerts,other blood glucose information, and/or the like regarding thehost-patient from server 130 (via for example the Internet and/orcellular network). Alternatively or additionally, smartwatch 199B mayreceive the alerts, other blood glucose information, and/or the likefrom a remote computer 198, smartphone, or other computer-based devicecoupled to network 120 and/or server 130. When this is the case, theremote computer 198 may use low energy links to communicate withsmartwatch 199B. Alternatively or additionally, smartwatch 199B mayreceive the alerts and other blood glucose information from thehost-patient's sensor assembly and/or receive (for example, receiver112) via for example cellular links and/or other types of wired and/orwireless links.

A transcutaneous analyte sensor system 100 comprising an on-skin sensorassembly 101 is fastened to the skin of a host via a disposable housing(not shown). The system includes a transcutaneous analyte sensor 102 anda transmitter/sensor electronics unit 104 for wirelessly transmittinganalyte information to a receiver or CGM receivers, such as devices110-113. Alternatively or additionally, the sensor may be non-invasive.Alternatively or additionally, analyte sensor 102 and atransmitter/sensor electronics unit 104 may be configured to wirelesslytransmit analyte information, such as continuous blood glucose data aswell as other types of data being monitored, directly to smartwatch199A.

During use, a sensing portion of the sensor 102 is under the host'sskin, and a contact portion of the sensor 102 is electrically connectedto the electronics unit 104. The electronics unit 104 engages a housing(not shown), and the sensor extends through the housing. The housing,which maintains the assembly 101 on the skin and provides for electricalconnection of the sensor 102 to sensor electronics provided in theelectronics unit 104, is attached to an adhesive patch fastened to theskin of the host.

The on-skin sensor assembly 101 may be attached to the host with anapplicator (not shown) adapted to provide convenient and secureapplication. Such an applicator may also be used for attaching theelectronics unit 104 to a housing, inserting the sensor 102 through thehost's skin, and/or connecting the sensor 102 to the electronics unit104. Once the electronics unit 104 is engaged with the housing and thesensor 102 has been inserted and is connected to the electronics unit104, the applicator detaches from the sensor assembly.

The continuous analyte sensor system 100 includes any sensorconfiguration that provides an output signal indicative of aconcentration of an analyte. The output signal, which may be in the formof, for example, sensor data, such as a raw data stream, filtered data,smoothed data, and/or otherwise transformed sensor data, is sent to areceiver, which is described in more detail below. In variousembodiments, the analyte sensor system 100 includes a transcutaneousglucose sensor, a subcutaneous glucose sensor, a continuous refillablesubcutaneous glucose sensor, or a continuous intravascular glucosesensor, for example.

In some embodiments, the sensor 102 extends through a housing (notshown), which maintains the sensor on the skin and provides forelectrical connection of the sensor-to-sensor electronics, provided inthe electronics unit 104. In some embodiments, the sensor 102 is formedfrom a wire. For example, the sensor can include an elongated conductivebody, such as a bare elongated conductive core (e.g., a metal wire) oran elongated conductive core coated with one, two, three, four, five, ormore layers of material, each of which may or may not be conductive. Theelongated sensor may be long and thin, yet flexible and strong. Forexample, in some embodiments the smallest dimension of the elongatedconductive body is less than about 0.1 inches, 0.075 inches, 0.05inches, 0.025 inches, 0.01 inches, 0.004 inches, or 0.002 inches. Amembrane system may be deposited over at least a portion ofelectroactive surfaces of the sensor 102 (including a working electrodeand optionally a reference electrode) and provides protection of theexposed electrode surface from the biological environment, diffusionresistance (limitation) of the analyte if needed, a catalyst forenabling an enzymatic reaction, limitation or blocking of interferents,and/or hydrophilicity at the electrochemically reactive surfaces of thesensor interface.

The membrane system may include a plurality of domains, for example, anelectrode domain, an interference domain, an enzyme domain (for example,including glucose oxidase), and a resistance domain, and can include ahigh oxygen solubility domain, and/or a bioprotective domain. Themembrane system may be deposited on the exposed electroactive surfacesusing known thin film techniques (for example, spraying,electro-depositing, dipping, etc.). In some embodiments, one or moredomains are deposited by dipping the sensor into a solution and drawingout the sensor at a speed that provides the appropriate domainthickness. However, the membrane system can be disposed over (ordeposited on) the electroactive surfaces using any known method.

In the illustrated example embodiment, the electronics unit 104 isreleasably attachable to the sensor 102, which together form the on-skinsensor assembly 101. The electronics unit 104 includes electroniccircuitry associated with measuring and processing the continuousanalyte sensor data, and is configured to perform algorithms associatedwith processing and calibration of the sensor data. The electronics unit104 may include hardware, firmware, and/or software that enablemeasurement of levels of the analyte via a glucose sensor, such as theanalyte sensor 102. For example, the electronics unit 104 can include apotentiostat, a power source for providing power to the sensor 102,other components useful for signal processing and data storage, andpreferably a telemetry module for one- or two-way data communicationbetween the electronics unit 104 and one or more receivers, repeaters,display devices, such as the devices 110-113, one or more smartphonessuch as smartphone 199A-B, and/or other devices. Sensor electronicswithin the electronics unit 104 can be affixed to a printed circuitboard (PCB), etc., and can take a variety of forms. For example, theelectronics can take the form of an integrated circuit (IC), such as anapplication-specific integrated circuit (ASIC), a microcontroller,and/or a processor. The electronics unit 104 may include sensorelectronics that are configured to process sensor information, such asstoring data, analyzing data streams, calibrating analyte sensor data,estimating analyte values, comparing estimated analyte values with timecorresponding measured analyte values, analyzing a variation ofestimated analyte values, such as estimated glucose values (EGVs),and/or the like.

The devices 110-113 may operate as repeaters, receivers, and/or displaydevices (also referred to herein more generally as “receivers” or “CGMreceivers”). In the example of FIG. 1, device 110 comprises a key fobrepeater 110, device 111 comprises a dedicated medical device receiver111, device 112 comprises a smartphone 112 including an application suchas a CGM application to provide the receiver disclosed herein, device113 comprises a portable or tablet computer 113 including an applicationsuch as a CGM application to provide the receiver disclosed herein,although other types of devices capable of receiving, repeating, and/ordisplaying the CGM sensor data provided by electronics unit 104 may beused as well. Moreover, although the previous example describes thesmartphone as including the CGM application, the other devices mayinclude a CGM application as well.

Devices 110-113 may be operatively linked (via wireless link(s), forexample) to the electronics unit 104. As noted above, the smartwatch199A may couple wireless directly to the wireless transceivers at thesensor assembly 101, in which case the smartwatch 199A may be considereda receiver. Alternatively or additionally, the smartwatch 199A may beconfigured to only couple wirelessly to a receiver 110-113.

The repeaters, receivers, and/or display devices 110-113 may receivedata from electronics unit 104, which is also referred to as thetransmitter and/or sensor electronics body herein. For example, thesensor data can be transmitted from the sensor electronics unit 104 toone or more of the key fob repeater 110, the medical device receiver111, the smartphone 112, the portable or tablet computer 113, smartwatch199A, and the like.

In some implementations, the repeaters, receivers and/or display devicesmay also transmit data to the electronics unit 104. In someimplementations, the repeaters, receivers, and/or display devices maytransmit data to one another or to other servers and/or computers. Forexample, smartphone 111 may receive CGM data from transmitter 104.Smartphone 111 may display the CGM data as well as related alerts andthe like. Smartphone 111 may also provide the CGM data to other devices,such devices 110, 112, 113, as well as one or more other servers, suchas secure server 130, via for example network 120. In some exampleembodiments, smartwatch 199A may be configured to transmit informationonly to a receiver, such as receiver 112. Alternatively or additionally,the smartwatch 199A may be configured to transmit to sensor assembly 101and/or server 130.

Data output from the output module 101 can provide wired and/orwireless, one or two-way communication between the receiver and anexternal computer. This external device can be any device thatinterfaces or communicates with the receiver. In some embodiments, theexternal device is a computer or a server, and the receiver is able todownload current and/or historical data for retrospective analysis by apatient, a caregiver, a physician, and/or the like for example. In someembodiments, the external device is a modem, and the receiver is able tosend alerts, warnings, emergency messages, etc., via telecommunicationlines to another party, such as a doctor and/or a family member. In someembodiments, the external device is an insulin pen or insulin pump, andthe receiver is able to communicate therapy recommendations, such as aninsulin amount and a time to the insulin pen or insulin pump. Theexternal device can include other technology or medical devices, forexample pacemakers, implanted analyte sensor patches, other infusiondevices, telemetry devices, etc. The receiver may communicate with otherdevices via any suitable communication technologies and/or protocolsincluding radio frequency (RF), Bluetooth, Bluetooth Low Energy, NFC(near field communications), universal serial bus (USB), any of thewireless local area network (WLAN) communication standards, includingthe IEEE 802.11, 802.15, 802.20, 802.22 and other 802 communicationprotocols, ZigBee, wireless (e.g., cellular) telecommunication, pagingnetwork communication, magnetic induction, satellite data communication,GPRS, 3G, 4G, 5G, LTE, ANT, and/or a proprietary communication protocol.

The server 130 may have at least one processor and at least one memorystorage device that receives, stores, and processes data received fromone or more of the key fob repeater 110, the medical device receiver111, the smartphone 112, the portable tablet computer 113, and otherdevices including the smartwatches 199A-B. The storage may comprise anytype of physical storage, such as RAM, DRAM, SRAM, a hard drive, and/orthe like. Moreover, the storage may include a database managementsystem, so that any data can be store in a database in a structured way.A remote device may couple to the server 130 to access sensor dataassociated with a given host-patient coupled to the sensor/transmitter.For example, a caregiver, a parent, and/or the like at a computer (orsmartwatch 199B coupled thereto) may receive, from the server 130 orother device, sensor data, reports, associated alerts, and the like toremotely follow a host-patient at receiver 112. The server may be securein the sense that a host-patient or other user trying to obtain thehost-patient's data may be required to login to the server with a useridentifier and a password before accessing sensor data, reports,associated alerts, and the like. Server 130 may also be secure in thesense that patient data may be secured in order to preserve a patient'sprivate data, such as patient identifiable data. The user interfaceviews (for example, a markup language page and/or the like) disclosedherein and/or the information for those views may be generated and/orprovided by the server 130, although other devices including a receiveror smartwatch may generate and/or provide the views as well.

The display device, such as a receiver, a smartwatch, and/or any otherdevice, may generate a user interface view for presentation at adisplay. This display device may include a CGM application configured togenerate user interface views including glance views, dashboards,handoff icons, and/or provide other operations including receive, at asmartwatch, an alert representative of a glucose state of a host-patientcoupled to a glucose sensor, detect, at the smartwatch, a predeterminedaction indicative of a request to generate a glance view providing anindication of the glucose state of the host-patient, and present, at thesmartwatch and in response to the detecting, the glance view providingthe indication of the glucose state of the host-patient. The userinterface view may include analyte values, such as CGM data, prompts ormessages to convey information to the user, such as reference outliervalues, requests for reference analyte values, therapy recommendations,deviation of the measured analyte values from the estimated analytevalues, CGM reports (for example, reports including CGM-relatedinformation for the host-patient), prompts to guide the user throughcalibration or troubleshooting of the calibration, and/or the like. Adevice, such as a smartwatch, receiver, computer, and/or any otherdevice, may download the CGM application, although the CGM applicationmay be provisioned in other ways as well (for example, pre-configuredduring manufacture and the like).

FIG. 2 is a functional block diagram of an embodiment of a system 200for leveraging mobile device features in continuous glucose monitoring,according to some example embodiments.

The system 200 may comprise a mobile device, which may be any type ofcomputing device capable of receiving one or more inputs and producingan output. Examples of the mobile device include a smartphone 112, atablet 113 computing device, a laptop, and/or the like. The mobiledevice 202 may include at least one memory 204 and at least oneprocessor 206. The memory 204 may provide the processor 206 access todata and program information that is stored in the memory 204 atexecution time. Typically, the memory 204 may include random accessmemory (RAM) circuits, read-only memory (ROM), flash memory, etc., or acombination thereof. The processor 206 may be, or may include, one ormore programmable general-purpose or special-purpose microprocessors206, digital signal processors 206 (DSPs), programmable controllers,application specific integrated circuits (ASICs), programmable logicdevices (PLDs), etc., or a combination of such hardware-based devices.The mobile device 202 may also include a display, such as a touchsensitive display 222 (also referred to herein as a touchscreen). Themobile device 202 may also include an interface 214 providing CGM data,and an output interface 220 to output data to other devices. Inaccordance with some embodiments, the processor 206 may execute acontinuous glucose monitoring (CGM) application 208 out of the memory204. In some example embodiments, the smartwatch 199A may be implementedas described with respect to FIG. 2.

In accordance with some embodiments, CGM application 208 may beconfigured to control, alone or in combination various aspects of thereceiver, smartwatch, and/or the like including receive, at asmartwatch, an alert representative of a glucose state of a host-patientcoupled to a glucose sensor, detect, at the smartwatch, a predeterminedaction indicative of a request to generate a glance view providing anindication of the glucose state of the host-patient, present, at thesmartwatch and in response to the detection, the glance view providingthe indication of the glucose state of the host-patient, providehandoffs, and/or the like. Moreover, the CGM application 208 may beconfigured to receive data from the transmitter, display CGM data,alerts, messages, and reports (for example, which may be generated bythe secure server or generated at the CGM application itself), transmit(or upload) data to other devices, such as server 130, and devices110-113, and receive data from other devices, such as server 130, anddevices 110-113.

In some example embodiments, the CGM application 208 may be downloadedonto the device 200 and comprise a dedicated application, although CGMapplication 208 may also comprise an internet browser configured toaccess via network 120 (for example, the Internet) the server 130. TheCGM application may also be configured to analyze CGM data provided by atransmitter as well as other data provided by other devices.

As used herein, the phrase “continuous glucose CGM application” shouldbe construed broadly to include not just the application itself, butalso integration with sensor 102, other diabetes management devices,including insulin delivery therapies such as insulin pumps, insulinpens, or other drugs useful for the treatment of diabetes. In otherwords, the CGM application may perform other functions besidesmonitoring blood glucose. It could, for example, determine that a user'sblood glucose level is high, and then transmit a signal to the user'sinsulin pump to administer a quantity of insulin to bring the user'sblood glucose level down.

A software and/or firmware component of the CGM application 208 may bestored in storage 210 available to the mobile device 202, and loadedinto the memory 204 at execution time. The storage 210 may be anynon-transitory computer readable media including, but not limited to, ahard disk, EEPROM (electrically erasable programmable read only memory),a memory stick, or any other storage device type. The memory 204 maycontain one or more data structures 212 that the CGM application 208accesses during execution. For example, the CGM application 208 mayreceive an input and store the input as an input parameter in a datastructure 212 in the memory 204 for later processing.

In some embodiments, the CGM application 208 may be embodied asdownloadable software that a user may download from a remote server,such as server 130, through a wired or wireless connection. For example,the user may access the server 130 using an application alreadyinstalled on the user's mobile device. The user may then download andinstall the CGM application 208 with the aid of the application. Theuser may then configure the CGM application 208. For example, theconfiguration may include setting the user's personal preferences and/orsettings, such as contacts, events, modes, profiles, and/or the like.The configuration may be done manually, such as by selecting variousoptions from menus, or automatically. In automatic configuration, theCGM application 208 reads the user's preferences and/or settings thatare stored on the mobile device. The CGM application 208 would firstdiscover what other applications are installed on the mobile device, andthen access those applications' data stored in the mobile device'sstorage and/or remote storage accessible by the mobile device 202 toinitially populate the CGM application 208 during set up.

Glance Views

The use of wearable device, such as smartwatches 199A-B and/or the like,may present issues with respect to display size. In the case of asmartwatch for example, the display size may be substantially smallerthan other user equipment, such as a smartphone. This small watchdisplay screen may make it difficult to display sufficient information.This small display may also make it more difficult to make a selectionvia the smartwatch screen. Although some of the examples refer tosmartwatches, other type of wearable devices may be used as well.

FIG. 3A depicts an example of a smartwatch 199A including a band 396, acase 398, which may include one or more circuits (not shown) such as atleast one processor circuit, at least one memory circuit, wirelesstransceiver(s), and/or other circuitry including touchscreen controlcircuitry, accelerometer/gyros, power management circuitry, a battery,and/or the like. The smartwatch 199A may also include a display, such astouch sensitive display 395, and include other input-output mechanisms,such as at least one physical button 394 that can be used as aninput/output device.

The smartwatch 199A may, as noted above with respect to FIG. 1, includeat least one low power transceiver for coupling wirelessly (for example,a Bluetooth transceiver, a Bluetooth Low Energy transceiver, an NFCtransceiver, and/or any other low power radio technology transceiver) toa receiver, such as receiver 112, 113, and/or the like, although otherhigher power radio technologies such as cellular and/or WiFi may be usedas well. The receiver, such as receiver 112, may comprise a smartphonethat includes a cellular radio transceiver or a WiFi transceiver forcoupling to other devices such as other receivers, server 130, and/orany other device, although the receiver may couple to server 130 viawired links as well. The receiver, such as receiver 112, may alsoinclude a lower power transceiver, such as a Bluetooth, Bluetooth LowEnergy, NFC, and/or the like, for coupling to the smartwatch 199A, aswell as other devices including a receiver, such as receiver 112, 113,and/or the like.

Moreover, the receiver, such as receiver 112, may send information, suchas alerts to the sensor 102, and the alerts may include a glucose highstate of the host-patient coupled to sensor 102, a glucose low state ofthe host-patient, and/or any other type of alert or information. Thealert may be presented at the smartwatch 199A and/or trigger a userinterface view, such as a graphical representation of the host-patient'sglucose state, an icon, a report, and/or other type of graphicalrepresentation.

In some example embodiments, there may be provided a so-called “glanceview.” For example, a specific gesture on the smartwatch touchscreen395, such as a swipe up or any other predetermined gesture (which may beconfigured via smartwatch 199A or via another device such as server 130,receiver 112, and/or remote follower 199B) may trigger presentation of acertain user interface view at the display screen 395 of the smartwatch199. In the example of FIG. 3A, an alert may be received at thesmartwatch 199A. This alert may automatically trigger an indication,such as haptic feedback (for example, vibration), audio feedback, and/ora graphical indication at the display 395. In response, a user may swipeacross, which may be a predetermined or preconfigured gesture on thetouchscreen display 395. This gesture may be detected by the smartwatchtouchscreen circuitry, and trigger the display of user interface view380. User interface view 380 may provide a so-called glance view becauseit gives the current glucose level at a glance. In the instant example,the glance view also includes two downward arrows indicate the relativerate that the glucose level is falling. More arrows would indicate afaster fall in the fall in the glucose level, while fewer arrows wouldindicate a slower rate of descent. A color, such as red, may also beused to indicate the low glucose level is below a threshold level, and anumerical value may also be presented as well.

Although the previous example refers to a gesture such as a swipe on theface of the smartwatch to trigger a certain user interface view such asa glance view, the glance view may be triggered by selection of acertain icon displayed on the smartwatch display 395 screen or aphysical button 394 on the smartwatch. In some example embodiments, theglance view may, as noted, be triggered by an accelerometer and/or gyrodetecting whether the smartwatch 199A is in view of the wearer's eyes byfor example monitoring wrist movement patterns. In some exampleembodiments, the glance view may be triggered by a camera sensor at thesmartwatch 199A detecting the wearer's eyes. Moreover, these events maytrigger additional data to be presented. For example, a glance view maybe presented on a smartwatch display, but a predetermined type of swipeof other event/action may trigger additional data to be presented, suchas more data to be displayed.

Although the previous example describes the glance view being triggeredby a gesture, icon selection, or other user-action, the glance view maybe presented at the display 395 automatically without the notedtriggers.

In some example embodiments, an accelerometer or gyroscope (gyro) in thesmartwatch may, as noted, detect patterns in the movement of the armand/or wrist. The detection may include detecting if a wearer of thesmartwatch holds the smartwatch in a certain position (or for a certaintime) so that the wearer can view the display of the smartwatch. If so,the smart watch may trigger a glance view or another type of a userinterface view without requiring the user to perform a physicalselection at the smartwatch.

In some example embodiments, a certain user interface view may beselected by the smartwatch 199A based on a type of alert, such as thestate of the host-patient. For example, if the host-patient has arapidly dropping blood glucose level as in FIG. 3A, a certain userinterface view 380 may be presented at the smartwatch display 395. Thissmartwatch 199A may map the user interface view 385 to the given alertor host-patient state, which in this example is a rapidly dropping bloodglucose level. To illustrate further, a rapidly rising blood glucoselevel alert may map to another user interface view, a fail toacknowledge an alert may map to another user interface view, and soforth.

Moreover, the type of user interface view presented at display 395 maybe dynamically selected. For example, as the state of the host-patientchanges (as indicated by alerts sent to the smartwatch, for example),the smartwatch 199A may select a certain user interface view based onthe host-patient's current state, and as that state changes the alertsand corresponding views presented at the display 395 may change as well.To illustrate, if the host-patient state changes to a high glucose stateor a normal glucose state, the smartwatch 199A may select another userinterface view to display as the glance view at 395.

In some example embodiments, the certain user interface view presentedas a glance view at display 395 may be selected by the smartwatch 199Abased on a role of the wearer of the smartwatch. For example, if thewearer of the smartwatch is the host-patient, a user interface view maybe presented on the smartwatch 199A display 395 for a high glucosestate. On the other hand, if the wearer of the smartwatch 199B is aremote follower, the remote follower's smartwatch 199B may present atdisplay 395 another type of user interface view for a high glucosestate. The type of user interface view selected and/or generated basedon role of the wearer of the smartwatch may be configured via thereceiver 112, smartwatch 199A, server 130, and/or any other device.Moreover, the configured user interface view selected for a given rolemay be configured by a user, configured as a default, and/or configuredor controlled by the server 130.

In some example embodiments, the smartwatch may dynamically zoom to aspecific portion of a log or overview report of a plot of glucosemeasurements.

In some example embodiments, the certain user interface view presentedas a glance view at display 395 may be selected by the smartwatch 199Abased on how the smartwatch is connected, such as whether the smartwatchis directly coupled to the receiver 112, to the cloud such ascloud-based server 130, and/or to the sensor 102. In some exampleembodiments, the certain user interface view may be selected by thesmartwatch based on the type of connection, such as cellular, WiFi, NFC,Bluetooth, Bluetooth Low Energy, and/or the like.

FIG. 3B illustrates an example of a smartwatch including a glance view,similar to smartwatch 199A of FIG. 3A, and a notification bar 399. Asshown in the figure, notification bar 399 may be located near the lowerend of display 395. In other embodiments, notification bar 399 may belocated near the upper end of display 395. In some embodiments,notification bar 399 may be hidden from display 395 until a user inputis performed. The user input may be performed in response to an alert,as will be discussed below in FIG. 3C. The user input can be a gesturefrom the user, such as a finger swipe. In some embodiments, the userinput can be a rotation or manipulation of button 394. For instance, anupward finger swipe, or a clockwise rotation of button 394, can causenotification bar 399 to scroll upwards. In some embodiments,notification bar 399 may instantaneously scroll or pop up upon detectionof an alert without a user input.

The glance view may direct the user's attention to the notification bar399 upon receiving the alert. For instance, the glance view may displayan arrow pointing to notification bar 399, display a glow nearnotification bar 399, display an animation near notification bar 399, orotherwise highlight the notification bar 399.

In some embodiments, notification bar 399 includes at least oneactionable selection. These actionable selections may be hidden in thebottom of the display 395 until the user gestures to scroll thenotification bar 399 upwards. As the user gestures to scrollnotification bar 399 upwards, notification bar 399 may gradually replacethe content of display 395 until all of the actionable selections ofnotification bar 399 are shown. As shown in FIG. 3B, notification bar399 can include multiple actions for the user to select. These actionscan include, for example: show map view, acknowledgement ofnotification, show trend view, phone call (or text message), and dismissnotification. The map view may display a map that indicates where thehost-patient is located. In some embodiments, the map view may indicatewhere at least one of the followers are located. The trend view maydisplay a glucose trend chart of the host-patient's glucose levels. Insome embodiments, the trend view may also display insulin dosageinformation.

FIG. 3C depicts an example process for generating certain user interfaceviews for a smartwatch, such as smartwatch 199A, in accordance with someexample embodiments. The description of FIG. 3C also refers to FIGS. 1and 3C.

At 352, the smartwatch 199A may generate and present, at display 395, acertain user interface view, such as a home screen or a default userinterface view providing certain data related to the receiver 112 orsensor 102, for example. To illustrate, the base view or default view ofhome screen may include a user interface view that the smartwatch isreceiving data from the sensor 102 and/or receiver 112. Alternatively oradditionally, the base view or default view may include an indication ofthe time and/or data.

At 354, the smartwatch 199A may receive an alert. For example, if thehost-patient's measured blood glucose level as determined by sensor 102measures a low blood glucose level and/or a glucose level that isdropping at a certain rate, an alert may be sent to the smartwatch 199A.The alert may be sent from the sensor 102 and/or receiver 112 to thesmartwatch 199A via a wireless link, which may comprise a low-power,short-range link (for example, NFC, Bluetooth, Bluetooth Low Energy,and/or the like), although a higher-power, longer range radio technologysuch as cellular, WiFi, and/or the like may be used as well.

At 356, a glance view corresponding to the received alert may bepresented at the display 395 of smartwatch 199A, and this glance view380 may be presented in response to an event detected at 356. Thedetected event may comprise receipt of the alert at 354. Alternativelyor additionally, the alert may trigger feedback (for example, haptic,audio, and/or visual feedback) to the wearer of smartwatch 199A, andthis feedback may prompt the user of the smartwatch 199A to perform aswipe gesture, for example. The event may be detected by touchscreencircuitry at the smartwatch 199A, and then trigger the display of glanceview 380. Alternatively or additionally, the glance view 380 may, asnoted above, be triggered by selection of a certain icon displayed onthe smartwatch display 395, a physical button 394, an accelerometerand/or gyro wrist movement detected patterns, a camera sensor at thesmartwatch 199A detecting the wearer's eyes, and/or any other event oraction.

At 358, the smartwatch 199A may present the glance view 380. In someexample embodiments, the smartwatch 199A may map different types ofglance views to different types of swipes. Moreover, certain types ofalerts for certain glucose states may be mapped to certain glance views.In addition, the display 395 may include certain icons that whenselected via the touchscreen 395 present certain glance views or certainblood glucose data reports. Furthermore, the severity of the glucosestate may be mapped to a certain glance view or detailed report. And,the smartwatch 199A may, as noted, map different types of glance viewsbased on the role of the wearer. For example, a remote follower atsmartwatch 199B may receive a simple message saying blood glucose levelis dangerously low, while the host-patient at smartwatch 199A mayreceive more detailed information such as glance view 380. In someexample embodiments, selecting glance view 380 may trigger a moredetailed report to be presented at smartwatch 199A or another device. Inaddition, the smartwatch may select a certain type of glance view basedon what the smartwatch is connected to. For example, if smartwatch 199Ais directly coupled to the receiver 112 and/or sensor 102, thesmartwatch 199A may present a certain type of glance view, but if thesmartwatch 199A is directly coupled to server 130, the smartwatch 199Amay be presented another type of glance view.

Dashboards

FIG. 4A depicts a smartwatch such as smartwatch 199B presenting adashboard of host-patients, in accordance with some example embodiments.In the example of FIG. 4A, the wearer of the smartwatch 199B may be aso-called remote follower. A remote follower's smartwatch 199B mayreceive from server 130 information, such as alerts and otherinformation for one or more host-patients, each of which may have asensor 102 and/or receiver 112, for example.

In the example of FIG. 4A, the dashboard includes icons 405 and 407A-Cfor 4 host-patients, labeled Pedro, J, J2, and B. In this way, a wearerof the smartwatch 199B may receive alerts, reports, glance views, and/orother information for the 4 host-patients. For example, selecting theicon 405 (labeled Pedro) presented on touchscreen 395 may provide aglance view, an alert, and/or other information including blood glucoseinformation for Pedro. Likewise, selecting the icon 407A (labeled B)presented on touchscreen 395 may provide a glance view, an alert, and/orother information including blood glucose information for Barbara, forexample.

In some example embodiments, the size of the graphical element, such asicon 405, may vary based on the quantity of hosts being followed by thewearer of watch 199B. For example, if the wearer is a remote followersuch as a teacher following 4 children, then the icons may have acertain, predetermined size, but if the teacher is following 11children, then the size of the icon representative of the host-patientsbeing followed by the teacher may be smaller as shown at FIG. 4B.

In some example embodiments, the order of the graphical elements ondisplay 395 may vary based on the severity of the current glucose stateof a host-patient. In the example of FIG. 4A, the host-patientrepresented by dashboard icon 405 may have a more severe glucose statethan the other host patients that are located in the lower portion ofthe screen. Referring again to FIG. 4B, it depicts that the dashboardicons for Amy and Pedro, which are the same size may be more severe thanthe other icons having smaller size and/or located below Amy and Pedro.For example, Amy and Pedro may have more severe glucose states based onthe larger size of the Amy and Pedro icons, when compared to the othericons on display 395 at FIG. 4B for host-patient's, such as G, J, J2,and so forth, which are smaller than Amy and Pedro's icons. In theexample of FIG. 4B, the arrangement of Amy and Pedro at the top portionof the dashboard display 395 may also indicate that Amy and Pedro mayhave more severe glucose, when compared to the other icons on display395 for host-patient's, such as G, J, J2, and so forth as these othericons are below Amy and Pedro's icons.

Although the previous example used order as the top of the touchscreendisplay, the order of the icons may be arranged in other ways, such asleft to right, right to left, bottom to top, or in any other way toindicate an ordered sequence of glucose severity for the host-patientsbeing monitored via the dashboard. Moreover, the order may be configuredby a user of the smartwatch, configured by the server, and/or configuredin other ways as well.

FIG. 4C depicts an example process for generating dynamic dashboards forthe smartwatch 199A-B, in accordance with some example embodiments. Thedescription of FIG. 4C also refers to FIGS. 1 and 4A-B.

At 452, the smartwatch, such as smartwatch 199B, may determine aquantity of followers being monitored via a dashboard view at thesmartwatch's display 395. The smartwatch may login to server 130, anddetermine alone or in combination with server 130 the quantity ofhost-patients (which have a sensor assembly and/or receiver) beingmonitored. For example, the smartwatch 199B may determine that it ismonitoring 4 host-patients (as in the example of FIG. 4A).

At 454, the smartwatch 199B may generate a display with icons sizedaccording to the determined quantity of followers. Based on thedetermined quantity, the smartwatch 199B may include a size model thatconfigures the size of the icons presented as a dashboard on thesmartwatch's touchscreen display. Referring again to FIG. 4A, if thequantity of 4 is determined, then the smartwatch 199B may configure thesize of the icons to be a first size, such as the size shown at FIG. 4A,but if the quantity of 11 is determined, then the smartwatch 199B mayconfigures the size of the icons to be another size, such as the sizeshown at FIG. 4B. Although the previous example refers to specificquantities, the dashboard may display other quantity of icons and sizethe icons accordingly.

At 456, an icon on dashboard may be selected via the touchscreen 395 orvia button 394, and this selection may, at 458, result in additionalinformation, such as a glance view, detailed report, or otherinformation for the selected icon. Referring to FIG. 4A for example, aselection of the icon 405 may be detected by touchscreen controlcircuitry, and this touch may trigger the display of a user interfaceview for that patient. Alternatively or additionally, button 394 may berotated and manipulated to move and select a given icon, such as icon405.

In some example embodiments, the user interface view may be anonymizedby using a code or other representation of the host-patient, rather thana host-patient's name. Referring again to the example at FIG. 4B, Pedromay correspond to number P1, while Amy may correspond to A2.Alternatively or additionally, patient identifying information may notbe displayed at the smartwatch. Referring again to FIG. 3A, the glucosestate of the host-patient may be displayed at 395 as a glance view 380,but the information may be presented without information identifying thehost-patient, such as name of the host-patient, serial number of thesensor or receiver, and/or any other of patient identifying information.

Referring again to FIG. 4A, the color of icon 405 may vary with theseverity of the host-patient's glucose state. Alternatively oradditionally, audio feedback associated with icon 405's touchscreenselection may vary with the severity of the host-patient's glucosestate. Alternatively or additionally, haptic feedback associated withicon 405's touchscreen selection may vary with the severity of thehost-patient's glucose state. Alternatively or additionally, icon 405may vary in some other graphically, audio, or haptically distinctive waybased on the severity of the host-patient's glucose state.

Handoffs

FIG. 5A depicts smartwatch 199A presenting a user interface view 380 ofhost-patient's blood glucose level, in accordance with some exampleembodiments. In the example of FIG. 5A, the wearer of the smartwatch mayenable smartwatch 199A and/or other locally connected devices, such asdevices connected via Bluetooth, WiFi, and/or the like, to allowhandoffs from the smartwatch 199A to another device. If the user of thesmartwatch 199A allows (for example, is configured to provide andenables the handoff) the handoff, the user may move to another device,such as receiver 112, and view the same user interface view 540.

In some example embodiments, the handoff may be enabled by selecting ahandoff icon 505A and/or B on the smartwatch 199A and/or receiver 112.When the handoff icon is selected 505, this allows the wearer to view atanother of the host-patient's devices, such as receiver 112, the userinterface view presented on the smartwatch 199A. For example, smartwatch199A may be wirelessly coupled via Bluetooth, Bluetooth Low Energy,WiFi, and/or cellular links to receiver 112. Moreover, both devices 199Aand receiver 112 may be logged in to server 130 and, in particular, thehost-patient's account including blood glucose data and other types ofdata for the patient. In this example selection of the handoff icon 505Aallows the host patient to view the user interface view 380 on anotherdevice, such as receiver 112.

In some example embodiments, selection of handoff icon 505A may send amessage to the other device. This message may comprise an index orindicator of what is being viewed currently at the smartwatch 199A. Whenthe other device such as smartphone 112 receives this message, thesmartphone 112 can determine what was being viewed. Although some of theexamples refer to handoff messages being exchanged directly between thelocally connected devices, the handoff message(s) may be sent to server130 as well to assist in the coordination of the handoff betweendevices, and display the proper content currently being viewed.

In some example embodiments, selection of handoff icon 505A may triggeranother type of user interface view that takes into account the displaysize on the other device. Referring to FIG. 5B, the handoff is toreceiver 112. During the handoff, the smartwatch 199A and receiver 112may exchange messages, as noted, wirelessly to coordinate the handoff.Next, the receiver 112 may present user interface view 550 thatincludes, due to the larger display area, additional information whencompared to user interface view 380. The type of user interface viewpresented at the receiver may be selected by the smartwatch 199A,receiver 112, and/or server 130. For example, if a user is viewing userinterface view 380 and selects a handoff, when the receiver 112 detectsthat the user seeks to resume viewing under a handoff condition,receiver 112 may send a message including an index to smartwatch 112(and/or server 130). This index may indicate what user interface view topresent at the receiver 112.

FIG. 5C depicts an example process for handoffs among devices, such assmartwatch 199A and smartphone 112, in accordance with some exampleembodiments. The description of FIG. 5C also refers to FIGS. 1 and 5A-B.

At 580, the smartwatch 199A may receive an alert. For example,smartwatch 199A may receive an alert from the sensor electronics 104and/or receiver 112, although the alert may be received from otherreceivers, devices, and/or server 130 as well. In response to thereceived alert, the smartwatch 199A may generate and present, at 582, acertain user interface view, such as a glance view 380 or a moredetailed view, such as a historical log of glucose levels over time. Ifthe smartwatch 199A and other device such as smartphone 112 haveconfigured, at 584, handoffs among devices and allow the handoffs, thesmartwatch 199A may send to the target device (which in this example issmartphone 112 to which the user is moving to for access), a messageindicating the content that is currently being viewed at smartphone199A. In some example embodiments, the message may comprise an indexpointing to the content being viewed on the smartwatch 199A that theuser would like to view at the smartphone 112. In some exampleembodiments, the server 130 may assist by serving content to thesmartphone 112 based on the message or index. In the example of FIG. 5A,the message or index may identify the user interface view 380. Toillustrate further, server 130 may have a table listing an index valuemapped to user interface view 380. As such, when the user hands off fromsmartwatch 199A to smartphone 112, the smartphone may request thecontent from the server 130 based on the index (or from the smartwatch199A directly without querying the sever 130).

At 586, the other device, such as smartphone 112, may present thecertain user interface view handed off by the smartwatch. Referring tothe previous example, the smartphone 112 may receive the content (fromserver 130 and/or smartwatch 199A) and present the handed off content,such as user interface view 380, at the smartphone 112.

Although the handoff may provide the same content, the content handedoff to another device may be different. In some example embodiments, thetarget device receiving the handed off content (such as smartphone 112in the previous example) may present a user interface view that may bedifferent when compared to what is presented at smartwatch 199A. Thetarget device smartphone 112 and/or server 130) may determine thatanother user interface view is more appropriate based on screen size (asnoted), as well as other factors, such as role of wearer of thesmartwatch 112, role of target device user (for example, a remotefollower may be presented a different view), severity of alert, a typeof gesture on the touchscreen, receipt of a certain type of alert, userpreferences, and/or other factors.

Although the previous example describes the handoff to the target devicebeing triggered by selection of a handoff icon, the handoff may beperformed automatically without the icon selection. For example, thesmartwatch 119 may be configured to handoff to other devices that thewearer of the device is logged into (as well as logged into server 130).

FIG. 6 depicts an example of a plurality of devices, which may all beassociated with the same host-patient. For example, the host-patient maybe being monitored by sensor assembly 101, which is wirelessly coupledto receiver 112. Moreover, the host-patient may be wearing smartwatch199A, and the host-patient may be using a tablet 113 or other type ofcomputer. These devices 101, 112, 199A, and 113 may all be locallyconnected via local links, such as NFC links, WiFi links, Bluetooth,Bluetooth Low Energy, and/or the like. For example, the devices 101,112, 199A, and 113 may all be located within the host-patient's home.Moreover, at each of the devices 101, 112, 199A, and 113, thehost-patient may be logged in his or her account at server 130 vianetwork 120 (for example, the internet, a cellular network, and/or othernetworks), so the host-patient is authenticated and authorized toreceive his or her alerts, blood glucose data, reports, and/or any otherinformation.

In some example embodiments, a master-slave scheme is provided toprioritize to what device 101, 112, 199A, and 113 an alert or userinterface view is generated and presented.

In some example embodiments, each device 101, 112, 199A, and 113 maydetect whether it is currently being used by the host-patient, and thedevice currently being used may signal the others that any alerts,reports, views, should be provided or sent to the device currently beingused. If the alert and/or the like is not acknowledge by a host-patient(for example, an icon selection on the display screen to acknowledge),the device currently being used may allow the other devices to generateand/or present alerts, reports, or views.

In some example embodiments, a user may specify a default orderindicating what device 101, 112, 199A, and 113 should first present analert, view, and/or report. If the alert and/or the like is notacknowledge by a host-patient (for example, an icon selection on thedisplay screen to acknowledge), the default order may specify which ofthe other devices should then present the alert.

In some example embodiments, the state of the host-patient may drivewhich device 101, 112, 199A, and 113 should first present an alarm,view, and/or report. For example, the order may include alerting asmartphone 112 or a remote follower's receiver or smartwatch.

In some example embodiments, the role of the user may drive which device101, 112, 199A, and 113 should first present an alarm, view, and/orreport. For example, the order may include alerting a remote follower'sreceiver or smartwatch.

In some example embodiments, the state of the device, such as availablepower, available connectivity, device health, and/or the like, may drivewhich device 101, 112, 199A, and 113 should first present an alarm,view, and/or report. For example, a device that is low in power or ishaving some other type of performance issue may be skipped in the order.

In some example embodiments, the smartwatch, such as smartwatch 199A-B,may be configured to handle data connection losses, alerts, poweroutages, power saving modes, and missed alerts differently based on therole of the wearer of the smartwatch.

In some example embodiments, there may be a default configuration, so acertain device is always alerted, such as smartwatch 199A. If the alertis not acknowledged after a certain time, the alert is resent to anotherdevice such as device 112 or another remote user, such as the wearer ofsmartwatch 119B. Moreover, a certain phone may be assigned as the masterto coordinate the scheme above.

In some example embodiments, there may be provided a way to let a userknow if a smartwatch 199A and/or a device 112 coupled to the smartwatch199A are not connected. For example, the link between watch andreceiver/smartphone may be monitored. Alternatively or additionally, aCGM application on the smartwatch or smartphone may be monitored. Insome example embodiments, a schedule may be configured on the devices.The device may provide for sleep time, wake up times, and the sending ofkeep alive (for example, phone tells watch to wake up periodically). Insome example embodiments, the smartwatch may provide health message tosmartphone 112 regarding power link status and/or the like.

In some example embodiments, the smartwatch 199A may have limitedfunctionality when compared to a smartphone or tablet based receiver112-113.

In some example embodiments, there may be provided actionablenotifications. For example, if a certain alert is received at asmartwatch, the smartwatch may have pre-generated and pre-populatedactionable notifications that prompt a user/wearer to act, such ascalling a host-patient, calling for emergency help, sending a text (forexample, eat an orange, call me or a doctor, etc.), and/or the like.Text could be prepopulated with a text statement or questions directedto the host. For non-limiting example, FIG. 3B depicts an embodiment ofactionable notifications that can be performed by the user.

FIG. 7 depicts an example block diagram of an apparatus 700, such assmartwatch 199A-B, in accordance with some example embodiments. Theapparatus may be implemented as a smartwatch as noted, but the apparatusmay comprise other types of user equipment as well.

The apparatus of FIG. 7 may include at least one processor 10. Theprocessor 10 may, for example, be embodied in a variety of waysincluding circuitry having one or more of the following: at least oneprocessing core, one or more microprocessors with accompanying digitalsignal processor(s), one or more processor(s) without an accompanyingdigital signal processor, one or more coprocessors, one or moremulti-core processors, one or more controllers, processing circuitry,one or more computers, various other processing elements includingintegrated circuits (for example, an application specific integratedcircuit (ASIC), a field programmable gate array (FPGA), and/or thelike), or some combination thereof. The apparatus 700 may include atleast one memory 12, such as volatile memory and/or non-volatile memory.The apparatus 700 may also include touchscreen controller circuitry 14for controlling the touchscreen display 19, detecting gestures includingtouches at the display 19, and/or the like. The apparatus 700 mayinclude at least one radio transceiver 16. The radio transceiver may beconfigured to transmit and/or receive in accordance with one or moreradio air interface standards, communication protocols, modulationtypes, access types, and/or the like. For example, the radiotransceiver(s) 16 be configured to provide one or more transceiverconfigured to operate in accordance with WiFi, 2G, 2.5G, 3G, 4G, 5G,Long Term Evolution (LTE), LTE Advanced, LTE-Direct, LTE-Unlicensed,infrared (IR), Bluetooth, wireless universal serial bus, Bluetooth LowEnergy, ZigBee, ANT, Near Field Communication (NFC), and/or the like.The apparatus 700 may also include a power management unit to managebattery use and charging of batteries powering the smartwatch. Theapparatus 700 may also include an accelerometer and/or gyro. Theapparatus 700 may also include other user interface elements includingan earphone or speaker, a ringer, a microphone, a display, a user inputinterface, a camera, and/or the like, all of which may be coupled to theprocessor 20.

Various implementations of the subject matter described herein may berealized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof. Thecircuitry may be affixed to a printed circuit board (PCB), or the like,and may take a variety of forms, as noted. These various implementationsmay include implementation in one or more computer programs that areexecutable and/or interpretable on a programmable system including atleast one programmable processor, which may be special or generalpurpose, coupled to receive data and instructions from, and to transmitdata and instructions to, a storage system, at least one input device,and at least one output device.

These computer programs (also known as programs, software, softwareapplications, or code) include machine instructions for a programmableprocessor, and may be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the term “machine-readable medium” refers toany non-transitory computer program product, apparatus and/or device(e.g., magnetic discs, optical disks, memory, Programmable Logic Devices(PLDs)) used to provide machine instructions and/or data to aprogrammable processor, including a machine-readable medium thatreceives machine instructions. The terms “tangible” and“non-transitory,” as used herein, are intended to describe acomputer-readable storage medium (or “memory”) excluding propagatingelectromagnetic signals, but are not intended to otherwise limit thetype of physical computer-readable storage device that is encompassed bythe phrase computer-readable medium or memory. For instance, the terms“non-transitory computer readable medium” or “tangible memory” areintended to encompass types of storage devices that do not necessarilystore information permanently, including for example, random accessmemory (RAM). Program instructions and data stored on a tangiblecomputer-accessible storage medium in non-transitory form may further betransmitted by transmission media or signals such as electrical,electromagnetic, or digital signals, which may be conveyed via acommunication medium such as a network and/or a wireless link.

To provide for interaction with a user, the subject matter describedherein may be implemented on a computer having a display device (e.g., aCRT (cathode ray tube) or LCD (liquid crystal display) monitor) fordisplaying information to the user and a keyboard and a pointing device(e.g., a mouse or a trackball) by which the user may provide input tothe computer. Other kinds of devices may be used to provide forinteraction with a user as well; for example, feedback provided to theuser may be any form of sensory feedback (e.g., visual feedback, audiblefeedback, or tactile feedback); and input from the user may be receivedin any form, including acoustic, speech, or tactile input.

The subject matter described herein may be implemented in a computingsystem that includes a back-end component (e.g., as a data server), orthat includes a middleware component (e.g., an application server), orthat includes a front-end component (e.g., a client computer having agraphical user interface or a Web browser through which a user mayinteract with an implementation of the subject matter described herein),or any combination of such back-end, middleware, or front-endcomponents. The components of the system may be interconnected by anyform or medium of digital data communication (e.g., a communicationnetwork). Examples of communication networks include a local areanetwork (“LAN”), a wide area network (“WAN”), and the Internet.

Although a few variations have been described in detail above, othermodifications are possible. For example, while the descriptions ofspecific implementations of the current subject matter discuss analyticapplications, the current subject matter is applicable to other types ofsoftware and data services access as well. Moreover, although the abovedescription refers to specific products, other products may be used aswell. In addition, the logic flows depicted in the accompanying figuresand described herein do not require the particular order shown, orsequential order, to achieve desirable results. Other implementationsmay be within the scope of the following claims.

For ease of explanation and illustration, in some instances the detaileddescription describes exemplary systems and methods in terms of acontinuous glucose monitoring environment; however it should beunderstood that the scope of the invention is not limited to thatparticular environment, and that one skilled in the art will appreciatethat the systems and methods described herein can be embodied in variousforms. Accordingly any structural and/or functional details disclosedherein are not to be interpreted as limiting the systems and methods,but rather are provided as attributes of a representative embodimentand/or arrangement for teaching one skilled in the art one or more waysto implement the systems and methods, which may be advantageous in othercontexts.

For example, and without limitation, described monitoring systems andmethods may include sensors that measure the concentration of one ormore analytes (for instance glucose, lactate, potassium, pH,cholesterol, isoprene, and/or hemoglobin) and/or other blood or bodilyfluid constituents of or relevant to a host and/or another party.

By way of example, and without limitation, monitoring system and methodembodiments described herein may include finger-stick blood sampling,blood analyte test strips, non-invasive sensors, wearable monitors (e.g.smart bracelets, smart watches, smart rings, smart necklaces orpendants, workout monitors, fitness monitors, health and/or medicalmonitors, clip-on monitors, and the like), adhesive sensors, smarttextiles and/or clothing incorporating sensors, shoe inserts and/orinsoles that include sensors, transdermal (i.e. transcutaneous) sensors,and/or swallowed, inhaled or implantable sensors.

In some embodiments, and without limitation, monitoring systems andmethods may comprise other sensors instead of or in additional to thesensors described herein, such as inertial measurement units includingaccelerometers, gyroscopes, magnetometers and/or barometers; motion,altitude, position, and/or location sensors; biometric sensors; opticalsensors including for instance optical heart rate monitors,photoplethysmogram (PPG)/pulse oximeters, fluorescence monitors, andcameras; wearable electrodes; electrocardiogram (EKG or ECG),electroencephalography (EEG), and/or electromyography (EMG) sensors;chemical sensors; flexible sensors for instance for measuring stretch,displacement, pressure, weight, or impact; galvanometric sensors,capacitive sensors, electric field sensors, temperature/thermal sensors,microphones, vibration sensors, ultrasound sensors,piezoelectric/piezoresistive sensors, and/or transducers for measuringinformation of or relevant to a host and/or another party.

Exemplary Apparatus, Methods, and Media

Method 1. A method comprising: receiving, at a smartwatch, an alertrepresentative of a glucose state of a host-patient coupled to a glucosesensor; detecting, at the smartwatch, a predetermined action indicativeof a request to generate a glance view providing an indication of theglucose state of the host-patient; and presenting, at the smartwatch andin response to the detecting, the glance view providing the indicationof the glucose state of the host-patient.

Method 2. The method of Method 1, wherein the alert is received via alow power radio access transceiver at the smartwatch.

Method 3. The method of Method 2, wherein the low power radio accesstransceiver is configured in accordance with at least one of Bluetooth,Bluetooth Low Energy, or NFC.

Method 4. The method of any one of Methods 2-3, wherein the alert isreceived from a receiver wirelessly coupled to the glucose sensor viatransmitter sensor electronics.

Method 5. The method of Method 4, wherein the receiver comprises atleast one of a smartphone and/or a tablet.

Method 6. The method of any one of Methods 4-5, wherein the receiverincludes a continuous blood glucose application configured to interactwith the smartwatch.

Method 7. The method of any one of Methods 1-6, wherein the alert isreceived from a remote server.

Method 8. The method of any one of Methods 1-7, wherein the detecting ofthe predetermined action triggers the smartwatch to replace a homescreen and/or a default user interface view with the glance view.

Method 9. The method of any one of Methods 1-8, further comprising:triggering, at the smartwatch and in response to the detecting, afeedback comprising a haptic indicator, an audio indicator, and/or avisual indicator.

Method 10. The method of any one of Methods 1-9, wherein thepredetermined action comprises a selection of a certain icon displayedon the smartwatch.

Method 11. The method of any one of Methods 1-10, wherein thepredetermined action comprises a selection of a physical button.

Method 12. The method of any one of Methods 1-11, wherein thepredetermined action comprises a detection of a certain wrist movement.

Method 13. The method of any one of Methods 1-12, wherein thepredetermined action comprises a detection of a certain eye movement ofa wearer of the smartwatch.

Method 14. The method of any one of Methods 1-13, further comprising:detecting a swipe pattern; mapping the detected swipe pattern to atleast one of a plurality of glance views, each of which is mapped to adifferent swipe pattern; and presenting, based on the detected swipepattern, the at least one glance view.

Method 15. The method of any one of Methods 1-14, further comprising:mapping the glucose state to at least one of a plurality of glanceviews, each of which is mapped to a different glucose state; andpresenting, based on the glucose state, the at least one glance view.

Method 16. The method of any one of Methods 1-15, further comprising:determining a role of a wearer of the smartwatch; mapping the role ofthe wearer to at least one of a plurality of glance views, each of whichis mapped to a different role; and presenting, based on the determinedrole, the at least one glance view.

Method 17. The method of any one of Methods 1-16, further comprising:presenting, based on what the smartwatch is directly coupled to, theglance view.

Method 18. The method of any one of Methods 1-17, wherein the glanceview provides, in a single user interface view, a graphical indicationof the glucose state including a rate of change of the glucose state.

Method 19. The method of Method 18, wherein the rate of change isrepresented by a quantity of arrows presented via the glance view, andwherein the glucose glance view further includes a current glucose valueof the host-patient.

Method 20. The method of any one of Methods 1-10, further comprising:generating a dashboard including a plurality of icons corresponding to aplurality of host-patients, each of which having a corresponding glucosestate.

Method 21. The method of Method 20, further comprising: selecting atleast one of the plurality of icons in order to obtain additionalinformation regarding the corresponding glucose state.

Method 22. The method of any one of Methods 20-21, further comprising:varying, based on a quantity of the plurality of icons, a size of theplurality of icons.

Method 23. The method of any one of Methods 20-22, further comprising:varying, based on a severity of the corresponding glucose state, anorder of presentation for the plurality of icons.

Method 24. The method of any one of Methods 1-23, further comprising:handing off the glance view displayed at the smartwatch to anotherdevice to enable presentation of the glance view at the other device.

Method 25. The method of any one of Methods 1-25, further comprising:presenting a notification bar in the glance view in response to thealert; and detecting a user input to view the notification bar.

Method 26. The method of Method 25, wherein the user input is a fingerswipe or a manipulation of a physical button.

Method 27. The method of any one of Methods 25-26, wherein thenotification bar includes at least one actionable selection.

Method 28. The method of any one of Methods 25-27, wherein theactionable selection displays a map, displays a glucose trend chart,acknowledges the alert, or dismisses the alert.

Method 29. A method comprising: determining a quantity of followersbeing monitored via a dashboard view presented at a display of thesmartwatch, the dashboard view including a plurality of iconscorresponding to a plurality of host-patients, each of which having acorresponding glucose state; generating a display including theplurality of icons sized according to the determined quantity offollowers; receiving a selection of a sized icon from among theplurality of icons; and displaying additional information regarding thecorresponding glucose state of the host-patient corresponding to theselected, sized icon.

Method 30. The method of Method 29, wherein an identity of each of theplurality of host-patients is anonymized.

Method 31. The method of any one of Methods 29-30, further comprisingdetecting, at the smartwatch, a predetermined action indicative of arequest to generate a glance view providing an indication of the glucosestate of the host-patient.

Method 32. The method of Method 31, further comprising presenting, atthe smartwatch and in response to the detecting, the glance viewproviding the indication of the glucose state of the host-patient.

Method 33. The method of Method 32, wherein the alert is received via alow power radio access transceiver at the smartwatch.

Method 34. The method of Method 33, wherein the low power radio accesstransceiver is configured in accordance with at least one of Bluetooth,Bluetooth Low Energy, or NFC.

Method 35. The method of any one of Methods 33-34, wherein the alert isreceived from a receiver wirelessly coupled to the glucose sensor viatransmitter sensor electronics.

Method 36. The method of Method 35, wherein the receiver comprises atleast one of a smartphone and/or a tablet.

Method 37. The method of any one of Methods 35-36, wherein the receiverincludes a continuous blood glucose application configured to interactwith the smartwatch.

Method 38 The method of Method 32, wherein the alert is received from aremote server.

Method 39. The method of any one of Methods 32-38, wherein the detectingof the predetermined action triggers the smartwatch to replace a homescreen and/or a default user interface view with the glance view.

Method 40. The method of any one of Methods 32-39, further comprising:triggering, at the smartwatch and in response to the detecting, afeedback comprising a haptic indicator, an audio indicator, and/or avisual indicator.

Method 41. The method of any one of Methods 32-40, wherein thepredetermined action comprises a selection of a physical button.

Method 42. The method of any one of Methods 32-41, wherein thepredetermined action comprises a detection of a certain wrist movement.

Method 43. The method of any one of Methods 32-42, wherein thepredetermined action comprises a detection of a certain eye movement ofa wearer of the smartwatch.

Method 44. The method of any one of Methods 32-43, further comprising:detecting a swipe pattern; mapping the detected swipe pattern to atleast one of a plurality of glance views, each of which is mapped to adifferent swipe pattern; and presenting, based on the detected swipepattern, the at least one glance view.

Method 45. The method of any one of Methods 32-44 further comprising:mapping the glucose state to at least one of a plurality of glanceviews, each of which is mapped to a different glucose state; andpresenting, based on the glucose state, the at least one glance view.

Method 46. The method of any one of Methods 32-45, further comprising:determining a role of a wearer of the smartwatch; mapping the role ofthe wearer to at least one of a plurality of glance views, each of whichis mapped to a different role; and presenting, based on the determinedrole, the at least one glance view.

Method 47. The method of any one of Methods 32-46, further comprising:presenting, based on what the smartwatch is directly coupled to, theglance view.

Method 48. The method of any one of Methods 32-47, wherein the glanceview provides, in a single user interface view, a graphical indicationof the glucose state including a rate of change of the glucose state.

Method 49. The method of Method 48, wherein the rate of change isrepresented by a quantity of arrows presented via the glance view, andwherein the glucose glance view further includes a current glucose valueof the host-patient.

Method 50. The method of any one of Methods 32-49, further comprisingvarying, based on a quantity of the plurality of icons, a size of theplurality of icons.

Method 51. The method of any one of Methods 32-50, further comprising:varying, based on a severity of the corresponding glucose state, anorder of presentation for the plurality of icons.

Method 52. The method of any one of Methods 32-51, further comprising:handing off the glance view displayed at the smartwatch to anotherdevice to enable presentation of the glance view at the other device.

Method 53. A method comprising: receiving, at a smartwatch, an alertrepresentative of a glucose state of a host-patient coupled to a glucosesensor; presenting, at the smartwatch, a user interface viewrepresentative of the glucose state; receiving a request to allow ahandoff of the presented user interface view to another device; andpresenting, at the other device and in response to the handoff, the userinterface view.

Method 54. The method of Method 53, wherein the handoff is enabled via aremote server.

Apparatus 55. An apparatus comprising: at least one processor includingat least one memory including program code which when executed by the atleast one processor causes operations comprising: receiving, at theapparatus, an alert representative of a glucose state of a host-patientcoupled to a glucose sensor; detecting, at the apparatus, apredetermined action indicative of a request to generate a glance viewproviding an indication of the glucose state of the host-patient; andpresenting, at the apparatus and in response to the detecting, theglance view providing the indication of the glucose state of thehost-patient.

Apparatus 56. The apparatus of Apparatus 55, wherein the apparatuscomprises a smartwatch.

Apparatus 57. The apparatus of Apparatus 56, wherein the alert isreceived via a low power radio access transceiver at the smartwatch.

Apparatus 58. The apparatus of Apparatus 57, wherein the low power radioaccess transceiver is configured in accordance with at least one ofBluetooth, Bluetooth Low Energy, or NFC.

Apparatus 59. The apparatus of any one of Apparatuses 57-58, wherein thealert is received from a receiver wirelessly coupled to the glucosesensor via transmitter sensor electronics.

Apparatus 60. The apparatus of Apparatus 59, wherein the receivercomprises at least one of a smartphone and/or a tablet.

Apparatus 61. The apparatus of any one of Apparatuses 59-60, wherein thereceiver includes a continuous blood glucose application configured tointeract with the smartwatch.

Apparatus 62. The apparatus of any one of Apparatuses 55-61, wherein thealert is received from a remote server.

Apparatus 63. The apparatus of any one of Apparatuses 56-62, wherein thedetecting of the predetermined action triggers the smartwatch to replacea home screen and/or a default user interface view with the glance view.

Apparatus 64. The apparatus of any one of Apparatuses 56-63, furthercomprising: triggering, at the smartwatch and in response to thedetecting, a feedback comprising a haptic indicator, an audio indicator,and/or a visual indicator.

Apparatus 65. The apparatus of any one of Apparatuses 56-64, wherein thepredetermined action comprises a selection of a certain icon displayedon the smartwatch.

Apparatus 66. The apparatus of any one of Apparatuses 56-65, wherein thepredetermined action comprises a selection of a physical button.

Apparatus 67. The apparatus of any one of Apparatuses 56-66, wherein thepredetermined action comprises a detection of a certain wrist movement.

Apparatus 68. The apparatus of any one of Apparatuses 56-67, wherein thepredetermined action comprises a detection of a certain eye movement ofa wearer of the smartwatch.

Apparatus 69. The apparatus of any one of Apparatuses 56-68, furthercomprising: detecting a swipe pattern; mapping the detected swipepattern to at least one of a plurality of glance views, each of which ismapped to a different swipe pattern; and presenting, based on thedetected swipe pattern, the at least one glance view.

Apparatus 70. The apparatus of any one of Apparatuses 56-70, furthercomprising: mapping the glucose state to at least one of a plurality ofglance views, each of which is mapped to a different glucose state; andpresenting, based on the glucose state, the at least one glance view.

Apparatus 71. The apparatus of any one of Apparatuses 56-70, furthercomprising: determining a role of a wearer of the smartwatch; mappingthe role of the wearer to at least one of a plurality of glance views,each of which is mapped to a different role; and presenting, based onthe determined role, the at least one glance view.

Apparatus 72. The apparatus of any one of Apparatuses 56-71, furthercomprising: presenting, based on what the smartwatch is directly coupledto, the glance view.

Apparatus 73. The apparatus of any one of Apparatus 56-73, wherein theglance view provides, in a single user interface view, a graphicalindication of the glucose state including a rate of change of theglucose state.

Apparatus 74. The apparatus of Apparatus 73, wherein the rate of changeis represented by a quantity of arrows presented via the glance view,and wherein the glucose glance view further includes a current glucosevalue of the host-patient.

Apparatus 75. The apparatus of any one of Apparatus 56-74, furthercomprising: generating a dashboard including a plurality of iconscorresponding to a plurality of host-patients, each of which having acorresponding glucose state.

Apparatus 76. The apparatus of any one of Apparatuses 56-75, furthercomprising: selecting at least one of the plurality of icons in order toobtain additional information regarding the corresponding glucose state.

Apparatus 77. The apparatus of any one of Apparatuses 56-76, furthercomprising: varying, based on a quantity of the plurality of icons, asize of the plurality of icons.

Apparatus 78. The apparatus of any one of Apparatuses 56-77, furthercomprising: varying, based on a severity of the corresponding glucosestate, an order of presentation for the plurality of icons.

Apparatus 79. The apparatus of any one of Apparatuses 56-78, furthercomprising: handing off the glance view displayed at the smartwatch toanother device to enable presentation of the glance view at the otherdevice.

Apparatus 80. An apparatus comprising: at least one processor includingat least one memory including program code which when executed by the atleast one processor causes operations comprising: determining a quantityof followers being monitored via a dashboard view presented at a displayof the smartwatch, the dashboard view including a plurality of iconscorresponding to a plurality of host-patients, each of which having acorresponding glucose state; generating a display including theplurality of icons sized according to the determined quantity offollowers; receiving a selection of a sized icon from among theplurality of icons; and displaying additional information regarding thecorresponding glucose state of the host-patient corresponding to theselected, sized icon.

Apparatus 81. The apparatus of Apparatus 80, wherein the apparatuscomprises a smartwatch.

Apparatus 82. The apparatus of any one of Apparatuses 80-81, wherein anidentity of each of the plurality of host-patients is anonymized.

Apparatus. 83. An apparatus comprising: at least one processor includingat least one memory including program code which when executed by the atleast one processor causes operations comprising: receiving, at theapparatus, an alert representative of a glucose state of a host-patientcoupled to a glucose sensor; presenting, at the apparatus, a userinterface view representative of the glucose state; receiving a requestto allow a handoff of the presented user interface view to anotherdevice; and presenting, at the other device and in response to thehandoff, the user interface view.

Apparatus 84. The apparatus of Apparatus 83, wherein the apparatuscomprises a smartwatch.

Apparatus 85. The apparatus of any one of Apparatuses 83-84, wherein thehandoff is enabled via a remote server.

Non-transitory computer readable storage medium 86. A non-transitorycomputer readable storage medium storing instructions that, whenexecuted by at least one programmable processor forming part of at leastone computing system, cause the at least one programmable processor toperform operations comprising: receiving an alert representative of aglucose state of a host-patient coupled to a glucose sensor; detecting apredetermined action indicative of a request to generate a glance viewproviding an indication of the glucose state of the host-patient; andpresenting, in response to the detecting, the glance view providing theindication of the glucose state of the host-patient.

Non-transitory computer readable storage medium 87. A non-transitorycomputer readable storage medium storing instructions that, whenexecuted by at least one programmable processor forming part of at leastone computing system, cause the at least one programmable processor toperform operations comprising: determining a quantity of followers beingmonitored via a dashboard view at a display of the apparatus, thedashboard view including a plurality of icons corresponding to aplurality of host-patients, each of which having a corresponding glucosestate; generating a display with the plurality of icons sized accordingto the determined quantity of followers; receiving a selection of asized icon from among the plurality of icons; and displaying additionalinformation regarding the corresponding glucose state of thehost-patient corresponding to the selected, sized icon host-patient.

Non-transitory computer readable storage medium 88. A non-transitorycomputer readable storage medium storing instructions that, whenexecuted by at least one programmable processor forming part of at leastone computing system, cause the at least one programmable processor toperform operations comprising: receiving an alert representative of aglucose state of a host-patient coupled to a glucose sensor; presentinga user interface view representative of the glucose state; receiving arequest to allow a handoff of the presented user interface view toanother device; and presenting, in response to the handoff, the userinterface view at another device.

Any of the features of any of the above-referenced methods, apparatus,and non-transitory computer readable storage media is applicable to allaspects and embodiments identified herein. Moreover, any of the featuresof the above-referenced methods, apparatus, and non-transitory computerreadable storage media is independently combinable, partly or whollywith any other of the above-referenced methods, apparatus, andnon-transitory computer readable storage media, in whole or in part.Further, any of the features of any of the above-referenced methods,apparatus, and non-transitory computer readable storage media may bemade optional to other aspects or embodiments. Any aspect or embodimentof a method can be performed by a system or apparatus of another aspector embodiment, any aspect or embodiment of a system or apparatus can beconfigured to perform a method of another aspect or embodiment, and anyaspect or embodiment of a media can be configured to perform a method ofanother aspect or embodiment.

While the disclosure has been illustrated and described in detail in thedrawings and foregoing description, such illustration and descriptionare to be considered illustrative or exemplary and not restrictive. Thedisclosure is not limited to the disclosed embodiments. Variations tothe disclosed embodiments can be understood and effected by thoseskilled in the art in practicing the claimed disclosure, from a study ofthe drawings, the disclosure and the appended claims.

All references cited herein are incorporated herein by reference intheir entirety. To the extent publications and patents or patentapplications incorporated by reference contradict the disclosurecontained in the specification, the specification is intended tosupersede and/or take precedence over any such contradictory material.

Unless otherwise defined, all terms (including technical and scientificterms) are to be given their ordinary and customary meaning to a personof ordinary skill in the art, and are not to be limited to a special orcustomized meaning unless expressly so defined herein. It should benoted that the use of particular terminology when describing certainfeatures or aspects of the disclosure should not be taken to imply thatthe terminology is being re-defined herein to be restricted to includeany specific characteristics of the features or aspects of thedisclosure with which that terminology is associated. Terms and phrasesused in this application, and variations thereof, especially in theappended claims, unless otherwise expressly stated, should be construedas open ended as opposed to limiting. As examples of the foregoing, theterm ‘including’ should be read to mean ‘including, without limitation,’‘including but not limited to,’ or the like; the term ‘comprising’ asused herein is synonymous with ‘including,’ ‘containing,’ or‘characterized by,’ and is inclusive or open-ended and does not excludeadditional, unrecited elements or method steps; the term ‘having’ shouldbe interpreted as ‘having at least;’ the term ‘includes’ should beinterpreted as ‘includes but is not limited to;’ the term ‘example’ isused to provide exemplary instances of the item in discussion, not anexhaustive or limiting list thereof; adjectives such as ‘known’,‘normal’, ‘standard’, and terms of similar meaning should not beconstrued as limiting the item described to a given time period or to anitem available as of a given time, but instead should be read toencompass known, normal, or standard technologies that may be availableor known now or at any time in the future; and use of terms like‘preferably,’ ‘preferred,’ ‘desired,’ or ‘desirable,’ and words ofsimilar meaning should not be understood as implying that certainfeatures are critical, essential, or even important to the structure orfunction of the invention, but instead as merely intended to highlightalternative or additional features that may or may not be utilized in aparticular embodiment of the invention. Likewise, a group of itemslinked with the conjunction ‘and’ should not be read as requiring thateach and every one of those items be present in the grouping, but rathershould be read as ‘and/or’ unless expressly stated otherwise. Similarly,a group of items linked with the conjunction ‘or’ should not be read asrequiring mutual exclusivity among that group, but rather should be readas ‘and/or’ unless expressly stated otherwise.

Where a range of values is provided, it is understood that the upper andlower limit, and each intervening value between the upper and lowerlimit of the range is encompassed within the embodiments.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity. The indefinite article “a” or “an” does not exclude aplurality. A single processor or other unit may fulfill the functions ofseveral items recited in the claims. The mere fact that certain measuresare recited in mutually different dependent claims does not indicatethat a combination of these measures cannot be used to advantage. Anyreference signs in the claims should not be construed as limiting thescope.

It will be further understood by those within the art that if a specificnumber of an introduced claim recitation is intended, such an intentwill be explicitly recited in the claim, and in the absence of suchrecitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral such a construction is intended in the sense one having skill inthe art would understand the convention (e.g., “a system having at leastone of A, B, or C” would include but not be limited to systems that haveA alone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.”

All numbers expressing quantities of ingredients, reaction conditions,and so forth used in the specification are to be understood as beingmodified in all instances by the term ‘about.’ Accordingly, unlessindicated to the contrary, the numerical parameters set forth herein areapproximations that may vary depending upon the desired propertiessought to be obtained. At the very least, and not as an attempt to limitthe application of the doctrine of equivalents to the scope of anyclaims in any application claiming priority to the present application,each numerical parameter should be construed in light of the number ofsignificant digits and ordinary rounding approaches.

Furthermore, although the foregoing has been described in some detail byway of illustrations and examples for purposes of clarity andunderstanding, it is apparent to those skilled in the art that certainchanges and modifications may be practiced. Therefore, the descriptionand examples should not be construed as limiting the scope of theinvention to the specific embodiments and examples described herein, butrather to also cover all modification and alternatives coming with thetrue scope and spirit of the invention.

What is claimed is:
 1. A method comprising: receiving, at a smartwatch,an alert representative of a glucose state of a host-patient coupled toa glucose sensor; detecting, at the smartwatch, a predetermined actionindicative of a request to generate a glance view providing anindication of the glucose state of the host-patient; and presenting, atthe smartwatch and in response to the detecting, the glance viewproviding the indication of the glucose state of the host-patient. 2.The method of claim 1, wherein the alert is received via a low powerradio access transceiver at the smartwatch.
 3. The method of claim 2,wherein the low power radio access transceiver is configured inaccordance with at least one of Bluetooth, Bluetooth Low Energy, or NFC.4. The method of claim 2, wherein the alert is received from a receiverwirelessly coupled to the glucose sensor via transmitter sensorelectronics.
 5. The method of claim 4, wherein the receiver comprises atleast one of a smartphone and/or a tablet.
 6. The method of claim 4,wherein the receiver includes a continuous blood glucose applicationconfigured to interact with the smartwatch.
 7. The method of claim 1,wherein the alert is received from a remote server.
 8. The method ofclaim 1, wherein the detecting of the predetermined action triggers thesmartwatch to replace a home screen and/or a default user interface viewwith the glance view.
 9. The method of claim 1, further comprising:triggering, at the smartwatch and in response to the detecting, afeedback comprising a haptic indicator, an audio indicator, and/or avisual indicator.
 10. The method of claim 1, wherein the predeterminedaction comprises a selection of a physical button.
 11. The method ofclaim 1, wherein the predetermined action comprises a detection of acertain wrist movement.
 12. The method of claim 1, wherein thepredetermined action comprises a detection of a certain eye movement ofa wearer of the smartwatch.
 13. The method of claim 1, furthercomprising: detecting a swipe pattern; mapping the detected swipepattern to at least one of a plurality of glance views, each of which ismapped to a different swipe pattern; and presenting, based on thedetected swipe pattern, the at least one glance view.
 14. The method ofclaim 1, further comprising: mapping the glucose state to at least oneof a plurality of glance views, each of which is mapped to a differentglucose state; and presenting, based on the glucose state, the at leastone glance view.
 15. The method of claim 1, further comprising:determining a role of a wearer of the smartwatch; mapping the role ofthe wearer to at least one of a plurality of glance views, each of whichis mapped to a different role; and presenting, based on the determinedrole, the at least one glance view.
 16. The method of claim 1, whereinthe glance view provides, in a single user interface view, a graphicalindication of the glucose state including a rate of change of theglucose state.
 17. The method of claim 1, further comprising: generatinga dashboard including a plurality of icons corresponding to a pluralityof host-patients, each of which having a corresponding glucose state.18. The method of claim 1, further comprising: presenting a notificationbar in the glance view in response to the alert; and detecting a userinput to view the notification bar.
 19. The method of claim 18, whereinthe user input is a finger swipe or a manipulation of a physical button.20. The method of claim 18, wherein the notification bar includes atleast one actionable selection.
 21. The method of claim 18, wherein theactionable selection displays a map, displays a glucose trend chart,acknowledges the alert, or dismisses the alert.
 22. A non-transitorycomputer readable storage medium storing instructions that, whenexecuted by at least one programmable processor forming part of at leastone computing system, cause the at least one programmable processor toperform operations comprising: receiving an alert representative of aglucose state of a host-patient coupled to a glucose sensor; detecting apredetermined action indicative of a request to generate a glance viewproviding an indication of the glucose state of the host-patient; andpresenting, in response to the detecting, the glance view providing theindication of the glucose state of the host-patient.
 23. Thenon-transitory computer readable storage medium of claim 22, wherein thealert is received via a low power radio access transceiver at thesmartwatch.
 24. The non-transitory computer readable storage medium ofclaim 22, wherein the alert is received from a receiver wirelesslycoupled to the glucose sensor via transmitter sensor electronics. 25.The non-transitory computer readable storage medium of claim 24, whereinthe receiver comprises at least one of a smartphone and/or a tablet. 26.The non-transitory computer readable storage medium of claim 24, whereinthe receiver includes a continuous blood glucose application configuredto interact with the smartwatch.
 27. The non-transitory computerreadable storage medium of claim 22, wherein the operations furthercomprise: presenting a notification bar in the glance view in responseto the alert; and detecting a user input to view the notification bar.28. The non-transitory computer readable storage medium of claim 27,wherein the user input is a finger swipe or a manipulation of a physicalbutton.
 29. The non-transitory computer readable storage medium of claim27, wherein the notification bar includes at least one actionableselection.
 30. The non-transitory computer readable storage medium ofclaim 27, wherein the actionable selection displays a map, displays aglucose trend chart, acknowledges the alert, or dismisses the alert.